Print

This update requires you to make changes to the following files:

• /Web.config
• /App_Config/Commands.config
• /App_Config/ConnectionStrings.config
• /App_Config/Include/Sitecore.Buckets.config
• /App_Config/Include/Sitecore.ContentSearch.config
• /App_Config/Include/Sitecore.Speak.config
• /App_Config/Include/Sitecore.ItemWebApi.config

Depending on search provider you should also update appropriate files below:

• Sitecore solution configured to use Lucene:
  • /App_Config/Include/Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config
  • /App_Config/Include/Sitecore.ContentSearch.Lucene.Index.Core.config
  • /App_Config/Include/Sitecore.ContentSearch.Lucene.Index.Master.config
  • /App_Config/Include/Sitecore.ContentSearch.Lucene.Index.Web.config
  • /App_Config/Include/Sitecore.ContentSearch.Lucene.Indexes.Sharded.Core.config.example
  • /App_Config/Include/Sitecore.ContentSearch.Lucene.Indexes.Sharded.Master.config.example
  • /App_Config/Include/Sitecore.ContentSearch.Lucene.Indexes.Sharded.Web.config.example
• Sitecore solution configured to use Solr:
  • /App_Config/Include/Sitecore.ContentSearch.Solr.Indexes.config

  The clean configuration files for Sitecore CMS and DMS 7.5 rev. 141003 can be downloaded using the following links:

• Web.config 
• app_config_files_75rev141003.zip 

Changes to Web.config

Tip: Most customers have only applied a small number of changes to the Web.config file. In that case, we recommend that you simply download the clean config file using the link above and re-apply any changes that you've made to save time and to reduce the risk of making mistakes when adding the new settings, pipelines, etc. to the file.

The following changes have been made to the web.config file of Sitecore CMS 7.5 rev. 141003 (Initial release) as compared to the web.config file of Sitecore CMS 7.2 rev. 1400526 (Update-2):

1. In the <events> section, add the following handler for event “item:added” at the end of handlers list:
   
   <handler type="Sitecore.Caching.Placeholders.PlaceholderCacheManager, Sitecore.Kernel" method="UpdateCaches" />
2. In the <events> section, add the following handler for event “item:added:remote” at the end of handlers list:
   
   <handler type="Sitecore.Caching.Placeholders.PlaceholderCacheManager, Sitecore.Kernel" method="UpdateCachesRemote" />
3. In the <events> section, add the following handler for event “item:deleted” at the end of handlers list:
   
   <handler type="Sitecore.Caching.Placeholders.PlaceholderCacheManager, Sitecore.Kernel" method="UpdateCaches" />
4. In the <events> section, add the following handler for event “item:deleted:remote” at the end of handlers list:
   
   <handler type="Sitecore.Caching.Placeholders.PlaceholderCacheManager, Sitecore.Kernel" method="UpdateCachesRemote" />
5. In the <events> section, add the following handler for event “item:saved” at the end of handlers list:
   
   <handler type="Sitecore.Caching.Placeholders.PlaceholderCacheManager, Sitecore.Kernel" method="UpdateCaches" />
6. In the <events> section, add the following handler for event “item:saved:remote” at the end of handlers list:
   
   <handler type="Sitecore.Caching.Placeholders.PlaceholderCacheManager, Sitecore.Kernel" method="UpdateCachesRemote" />
7. In the <events> section, add the following events after the <event name="example"> element:
   
   <!-- sessionEnd:starting
       Raised before the sessionEnd pipeline is executed. -->
   <event name="sessionEnd:starting" />
   <!-- sessionEnd:postSessionEnd:starting
       Raised before the postSessionEnd pipeline is executed. -->
   <event name="sessionEnd:postSessionEnd:starting" />
   <!-- sessionEnd:ended
       Raised after the sessionEnd pipeline has been executed. -->
   <event name="sessionEnd:ended" />
8. In the <pipelines> section, add the following pipeline, after the <sessionEnd> element:
   
   <postSessionEnd>
   </postSessionEnd>
9. In the pipeline findVisitorEmailAddress replace processor
   
   <processor type="Sitecore.Pipelines.GetVisitorEmailAddress.FindVisitorEmailAddress, Sitecore.Kernel" method="FindEmailInUserProfile" />
   with the following one:
   
   <processor type="Sitecore.Pipelines.GetVisitorEmailAddress.FindContactEmailAddress, Sitecore.Kernel" method="FindEmailInUserProfile" />
10. In the <system.webServer><modules> section replace element
    
    <add type="Sitecore.Analytics.Media.MediaRequestSessionModule, Sitecore.Analytics" name="MediaRequestSessionModule" />
    with the following one:
    
    <add type="Sitecore.Analytics.RobotDetection.Media.MediaRequestSessionModule, Sitecore.Analytics.RobotDetection" name="MediaRequestSessionModule" />
11. In the <system.web><httpModules> section replace element
    
    <add type="Sitecore.Analytics.Media.MediaRequestSessionModule, Sitecore.Analytics" name="MediaRequestSessionModule" />
    with the following one:
    
    <add type="Sitecore.Analytics.RobotDetection.Media.MediaRequestSessionModule, Sitecore.Analytics.RobotDetection" name="MediaRequestSessionModule" />
12. In the <system.web><compilation><assemblies> section, add the following elements:
    
    <add assembly="System.Web.Http, Version=5.1.0.0, Culture=neutral,PublicKeyToken=31BF3856AD364E35" />
    <add assembly="System.Web.Http.WebHost, Version=5.1.0.0, Culture=neutral,PublicKeyToken=31BF3856AD364E35" />
    <add assembly="System.Net.Http.Formatting, Version=5.1.0.0, Culture=neutral,PublicKeyToken=31BF3856AD364E35" />
    After this change, the <assemblies> section looks like this in a clean Sitecore installation:
    
    <assemblies>
     <add assembly="System.Web.Abstractions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
     <add assembly="System.Web.Routing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
     <add assembly="System.Data.Linq, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
     <add assembly="System.Web.Helpers, Version=3.0.0.0, Culture=neutral,PublicKeyToken=31BF3856AD364E35" />
     <add assembly="System.Web.Mvc, Version=5.1.0.0, Culture=neutral,PublicKeyToken=31BF3856AD364E35" />
     <add assembly="System.Web.WebPages, Version=3.0.0.0, Culture=neutral,PublicKeyToken=31BF3856AD364E35" />
     <add assembly="System.Web.WebPages.Razor, Version=3.0.0.0, Culture=neutral,PublicKeyToken=31BF3856AD364E35" />
     <add assembly="System.Web.Http, Version=5.1.0.0, Culture=neutral,PublicKeyToken=31BF3856AD364E35" />
     <add assembly="System.Web.Http.WebHost, Version=5.1.0.0, Culture=neutral,PublicKeyToken=31BF3856AD364E35" />
     <add assembly="System.Net.Http.Formatting, Version=5.1.0.0, Culture=neutral,PublicKeyToken=31BF3856AD364E35" />
    </assemblies>
13. In the <system.web> section, change the <sessionState> element, so it looks like this in a clean Sitecore installation:
    
    <!-- SESSION STATE SETTINGS
         By default ASP .NET uses cookies to identify which requests belong to a particular session.
         If cookies are not available, a session can be tracked by adding a session identifier to the URL.
         To disable cookies, set sessionState cookieless="true".
         Note that Sitecore does not support cookieless sessions
         <sessionState mode="InProc" cookieless="false" timeout="20"/>
         <sessionState mode="StateServer" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa;password=" cookieless="false" timeout="20"/>
    -->
    <sessionState mode="InProc" cookieless="false" timeout="20">
     <providers>
       <add name="mongo" type="Sitecore.SessionProvider.MongoDB.MongoSessionStateProvider, Sitecore.SessionProvider.MongoDB" sessionType="Standard" connectionStringName="session" pollingInterval="2" compression="false" />
       <add name="mssql" type="Sitecore.SessionProvider.Sql.SqlSessionStateProvider, Sitecore.SessionProvider.Sql" sessionType="Standard" connectionStringName="session" pollingInterval="2" compression="false" />
     </providers>
    </sessionState>
14. In the <runtime><assemblyBinding> section add the following elements at the end of the list:
    
    <dependentAssembly>
     <assemblyIdentity name="System.Web.Http" publicKeyToken="31bf3856ad364e35" xmlns="urn:schemas-microsoft-com:asm.v1" />
     <bindingRedirect oldVersion="1.0.0.0-5.0.0.0" newVersion="5.1.0.0" xmlns="urn:schemas-microsoft-com:asm.v1" />
    </dependentAssembly>
    <dependentAssembly>
     <assemblyIdentity name="System.Web.Http.WebHost" publicKeyToken="31bf3856ad364e35" xmlns="urn:schemas-microsoft-com:asm.v1" />
     <bindingRedirect oldVersion="1.0.0.0-5.0.0.0" newVersion="5.1.0.0" xmlns="urn:schemas-microsoft-com:asm.v1" />
    </dependentAssembly>
    <dependentAssembly>
     <assemblyIdentity name="System.Net.Http.Formatting" publicKeyToken="31bf3856ad364e35" xmlns="urn:schemas-microsoft-com:asm.v1" />
     <bindingRedirect oldVersion="1.0.0.0-5.0.0.0" newVersion="5.1.0.0" xmlns="urn:schemas-microsoft-com:asm.v1" />
    </dependentAssembly>
    
    If you have not updated bindingRedirect for Newtonsoft.Json as mentioned in the upgrade guide, update it to the following:
    
    <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
    After this change, <runtime><assemblyBinding> section looks like this in a clean Sitecore installation:
    
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
     <dependentAssembly>
       <assemblyIdentity name="Lucene.Net" publicKeyToken="85089178b9ac3181" />
       <bindingRedirect oldVersion="0.0.0.0-2.9.4.0" newVersion="3.0.3.0" />
     </dependentAssembly>
     <dependentAssembly>
       <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" />
       <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
     </dependentAssembly>
     <dependentAssembly>
       <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" xmlns="urn:schemas-microsoft-com:asm.v1" />
       <bindingRedirect oldVersion="1.0.0.0-5.0.0.0" newVersion="5.1.0.0" xmlns="urn:schemas-microsoft-com:asm.v1" />
     </dependentAssembly>
     <dependentAssembly>
       <assemblyIdentity name="System.Web.WebPages.Razor" publicKeyToken="31bf3856ad364e35" xmlns="urn:schemas-microsoft-com:asm.v1" />
       <bindingRedirect oldVersion="1.0.0.0-3.0.0.0" newVersion="3.0.0.0" xmlns="urn:schemas-microsoft-com:asm.v1" />
     </dependentAssembly>
     <dependentAssembly>
       <assemblyIdentity name="System.Web.Http" publicKeyToken="31bf3856ad364e35" xmlns="urn:schemas-microsoft-com:asm.v1" />
       <bindingRedirect oldVersion="1.0.0.0-5.0.0.0" newVersion="5.1.0.0" xmlns="urn:schemas-microsoft-com:asm.v1" />
     </dependentAssembly>
     <dependentAssembly>
       <assemblyIdentity name="System.Web.Http.WebHost" publicKeyToken="31bf3856ad364e35" xmlns="urn:schemas-microsoft-com:asm.v1" />
       <bindingRedirect oldVersion="1.0.0.0-5.0.0.0" newVersion="5.1.0.0" xmlns="urn:schemas-microsoft-com:asm.v1" />
     </dependentAssembly>
     <dependentAssembly>
       <assemblyIdentity name="System.Net.Http.Formatting" publicKeyToken="31bf3856ad364e35" xmlns="urn:schemas-microsoft-com:asm.v1" />
       <bindingRedirect oldVersion="1.0.0.0-5.0.0.0" newVersion="5.1.0.0" xmlns="urn:schemas-microsoft-com:asm.v1" />
     </dependentAssembly>
    </assemblyBinding>

Changes to App_Config\Commands.config

Tip: Most customers have only applied a small number of changes (if any) to the Commands.config file. In that case, we recommend that you simply download the clean config file using the link above and re-apply any changes that you've made to save time and to reduce the risk of making mistakes when the changes to the file.

The following changes have been made to the App_Config\Commands.config file of Sitecore CMS 7.5 rev. 141003 (Initial Release) as compared to the App_Config\Commands.config file of Sitecore CMS 7.2 rev. 140526 (Update-2).

1. Remove the command “analytics:runlookup”.
2. Remove the command “analytics:runvisitoridentification”.
3. Remove the command “analytics:synchronizedatabase”.
4. Remove the command “analytics:updatereports”.

Changes to App_Config\ConnectionStrings.config

The following changes have been made to the App_Config\ConnectionStrings.config file of Sitecore CMS 7.5 rev. 141003 (Initial Release) as compared to the App_Config\ConnectionStrings.config file of Sitecore CMS 7.2 rev. 140526 (Update-2).

Add the following nodes after the <add name="web" …> node:

<add name="analytics" connectionString="mongodb://localhost/analytics" />
<add name="tracking.live" connectionString="mongodb://localhost/tracking_live" />
<add name="tracking.history" connectionString="mongodb://localhost/tracking_history" />
<add name="reporting" connectionString="user id=user;password=password;Data Source=(server);Database=Sitecore_Analytics" />

After this change, <connectionStrings> section looks like this in a clean Sitecore installation:

<connectionStrings>
 <!--
   Sitecore connection strings.
   All database connections for Sitecore are configured here.
 -->
 <add name="core" connectionString="user id=user;password=password;Data Source=(server);Database=Sitecore_Core" />
 <add name="master" connectionString="user id=user;password=password;Data Source=(server);Database=Sitecore_Master" />
 <add name="web" connectionString="user id=user;password=password;Data Source=(server);Database=Sitecore_Web" />
 <add name="analytics" connectionString="mongodb://localhost/analytics" />
 <add name="tracking.live" connectionString="mongodb://localhost/tracking_live" />
 <add name="tracking.history" connectionString="mongodb://localhost/tracking_history" />
 <add name="reporting" connectionString="user id=user;password=password;Data Source=(server);Database=Sitecore_Analytics" />
</connectionStrings>

Changes to App_Config\Include\Sitecore.Buckets.config

Tip: Most customers have only applied a small number of changes (if any) to the Sitecore.Buckets.config file. In that case, we recommend that you simply download the clean config file using the link above and re-apply any changes that you've made to save time and to reduce the risk of making mistakes when adding the new settings, pipelines, etc. to the file.

The following changes have been made to the App_Config\Include\Sitecore.Buckets.config file of Sitecore CMS 7.5 rev. 141003 (Initial Release) as compared to the App_Config\Include\Sitecore.Buckets.config file of Sitecore CMS 7.2 rev. 140526 (Update-2).

In the <pipelines> section, remove the following processors in the <buckets.dynamicFields> pipeline:

<!-- Allows users to place "TestResults" in their views and show whether or not the results are for all the tests currently running on this item. -->
<processor type="Sitecore.Buckets.Pipelines.UI.DynamicFields.TestResults, Sitecore.Buckets"/>
<!-- Allows users to place "EngagementValue or Visits" in their views and show the engagement value of the item or the number of visits it has received.-->
<processor type="Sitecore.Buckets.Pipelines.UI.DynamicFields.EngagementValue, Sitecore.Buckets"/>

After this change, <pipelines><buckets.dynamicFields> pipeline looks like this in a clean Sitecore installation:

Changes to App_Config\Include\Sitecore.ContentSearch.config

Tip: Most customers have only applied a small number of changes (if any) to the Sitecore.ContentSearch.config file. In that case, we recommend that you simply download the clean config file using the link above and re-apply any changes that you've made to save time and to reduce the risk of making mistakes when adding the new settings, pipelines, etc. to the file.

The following changes have been made to the App_Config\Include\Sitecore.ContentSearch.config file of Sitecore CMS 7.5 rev. 141003 (Initial Release) as compared to the App_Config\Include\Sitecore.ContentSearch.config file of Sitecore CMS 7.2 rev. 140526 (Update-2).

1. In the <pipelines> section, add the following pipeline, after the <contentSearch.translateQuery> pipeline:
   
   <!-- CONTENT SEARCH - CLEAN UP
       This pipeline allows you to modify the data of an IIndexable before the document builder processes it. For example, you can use
       this pipeline to de-duplicate, merge, or override data.
       Arguments : (IIndexable) The document being indexed, (IProviderUpdateContext) The open update context for the index, (bool) A flag
       that indicates if the IIndexable was modified during the process
   -->
   <contentSearch.cleanUp>
    <processor type="Sitecore.ContentSearch.Pipelines.CleanUp.ApplyCleanUp, Sitecore.ContentSearch"/>
   </contentSearch.cleanUp>
2. A comment for the agent in <scheduling> section has been added. We recommend that you add the comment to keep your file up-to-date, but this step does not affect the functionality of the system. In a clean Sitecore installation, the <scheduling > section now looks like this:
   
   <scheduling>
    <!-- An agent to optimize the specified indexes periodically. -->
    <agent type="Sitecore.ContentSearch.Tasks.Optimize" method="Run" interval="01:00:00">
      <indexes hint="list">
        <index>sitecore_master_index</index>
      </indexes>
    </agent>
   </scheduling>
3. In the <settings> section, remove the following setting:
   
   <!-- CONTENT SEARCH DATE FORMAT
        When processing DateTime types, the format that the date should be stored in.
   -->
   <setting name="ContentSearch.DateFormat" value="yyyyMMdd" />
4. In the <settings> section, add the following settings after the “Search.UseLegacySearchEngine” setting:
   
   <!-- CONTENT SEARCH - DEFAULT INDEX TYPE
        This setting specifies the index type that should be used when an item appears in more than one index.
   -->
   <setting name="ContentSearch.DefaultIndexType" value="Sitecore.ContentSearch.LuceneProvider.LuceneIndex, Sitecore.ContentSearch.LuceneProvider" />
   
   <!-- CONTENT SEARCH - DEFAULT INDEX CONFIGURATION PATH
       This setting specifies an XPath expression that points to the default index configuration. The default configuration is used for
       every index that does not have a specified configuration.
   -->
   <setting name="ContentSearch.DefaultIndexConfigurationPath" value="contentSearch/indexConfigurations/defaultLuceneIndexConfiguration" />

Changes to App_Config\Include\Sitecore.Speak.config

Tip: Most customers have only applied a small number of changes (if any) to the Sitecore.Speak.config file. In that case, we recommend that you simply download the clean config file using the link above and re-apply any changes that you've made to save time and to reduce the risk of making mistakes when the changes to the file.

The following changes have been made to the App_Config\Include\Sitecore.Speak.config file of Sitecore CMS 7.5 rev. 141003 (Initial Release) as compared to the App_Config\Include\Sitecore.Speak.config file of Sitecore CMS 7.2 rev. 140526 (Update-2).

1. In the <sitecore> section, remove the <overrideXmlControls> element.
2. In the <sitecore> section, remove the <overrideDialogs> element.
3. In the <sitecore> section, add the following settings at the beginning of the settings list:
   
   <!-- SPEAK COMPONENT COMPONENT PRESENTER
        The name of the Component Presenter.
        Default: scComponentPresenter
   -->
   <setting name="Speak.Components.ComponentPresenter" value="scComponentPresenter"/>
   
   <!-- SPEAK COMPONENT KNOCKOUT PRESENTER
        The name of the Knockout Presenter.
        Default: scKoPresenter
   -->
   <setting name="Speak.Components.KnockoutPresenter" value="scKoPresenter"/>
   
   <!-- SPEAK COMPONENT SPEAK PRESENTER
        The name of the SPEAK Presenter.
        Default: scSpeakPresenter
   -->
   <setting name="Speak.Components.SpeakPresenter" value="scSpeakPresenter"/>
4. In the <settings> section, change the “Speak.Html.RequireJsMainFile” setting, so it looks like this in a clean Sitecore installation:
   
   <!-- SPEAK HTML REQUIRE JS MAIN FILE
          Specifies the path of the main.js version SPEAK 1.2 file which configures Require.js.
          Default: /-/speak/v1/assets/main-1.2.js
   -->
   <setting name="Speak.Html.RequireJsMainFile" value="/-/speak/v1/assets/main-1.2.js"/>
5. In the <settings> section, add the following settings after the “Speak.Html.RequireJsMainFile” setting:
   
   <!-- SPEAK HTML REQUIRE JS MAIN FILE MINIFIED
        Specifies the path of the minfied SPEAK version for 1.2 of main.js file which configures Require.js.
        Default: /-/speak/v1/assets/main-1.2.min.js
   -->
   <setting name="Speak.Html.RequireJsMainFileMinified" value="/-/speak/v1/assets/main-1.2.min.js"/>
   
   <!-- SPEAK BINDING JS FILE
        Specifies the path of the binding plugin required by SPEAK to apply bindings.
        Default: /sitecore/shell/client/Speak/Assets/lib/core/1.2/deps/scBindingPlugin.js
   -->
   <setting name="Speak.Html.BindingPluginFile" value="/sitecore/shell/client/Speak/Assets/lib/core/1.2/deps/scBindingPlugin.js"/>
   
   <!-- SPEAK BINDING JS FILE MINIFIED
        Specifies the path of the binding plugin minified required by SPEAK to apply bindings.
        Default: /sitecore/shell/client/Speak/Assets/lib/core/1.2/deps/scBindingPlugin.min.js
   -->
   <setting name="Speak.Html.BindingPluginFileMinified" value="/sitecore/shell/client/Speak/Assets/lib/core/1.2/deps/scBindingPlugin.min.js"/>
   
   <!-- THE MAIN FILE for the CMS 7.1
        Specifies the path of the main.js file which configures Require.js.
        Default: /-/speak/v1/assets/main.js
   -->
   <setting name="Speak.Html.RequireJSBackwardCompatibilityFile" value="/-/speak/v1/assets/main.js"/>
6. In the <settings> section, add the following setting after the “IsProductionMode” setting:
   
   <!-- MASTER RENDERING ID
        The item ID of the Master rendering, which can be expanded.
        Default: {5AA4AD6B-1228-45C1-B4C3-B1847AE60FA2}
   -->
   <setting name="Speak.Mvc.MasterRenderingID" value="{3DC89CCA-D94A-4C46-A16D-AF6D0CB7E721}" />
7. In the <pipelines> section, remove the following processors from the <preprocessRequest> pipeline:
   
   <processor type="Sitecore.Pipelines.HttpRequest.OverrideDialogs, Sitecore.Speak.Client" />
   <processor type="Sitecore.Pipelines.HttpRequest.OverrideXmlControl, Sitecore.Speak.Client" />
   
   After this change, <pipelines><preprocessRequest> pipeline looks like this in a clean Sitecore installation:
   <preprocessRequest>
    <processor type="Sitecore.Pipelines.HttpRequest.ResolveClientPath, Sitecore.Speak.Client" />
   </preprocessRequest>
8. In the <pipelines> section, add the following processors to <speak.client.parseRenderingParameter> pipeline at the end of the processors list:
   
   <processor type="Sitecore.Web.Pipelines.SetAttribute.ParseContextItemValue, Sitecore.Speak.Client" />
   <processor type="Sitecore.Web.Pipelines.SetAttribute.ParseFormValue, Sitecore.Speak.Client" />
   <processor type="Sitecore.Web.Pipelines.SetAttribute.ParseQueryStringValue, Sitecore.Speak.Client" />
   <processor type="Sitecore.Web.Pipelines.SetAttribute.ParseSessionValue, Sitecore.Speak.Client" />
   <processor type="Sitecore.Web.Pipelines.SetAttribute.ParseAppModelValue, Sitecore.Speak.Client" />
   <processor type="Sitecore.Web.Pipelines.SetAttribute.ParsePageModelValue, Sitecore.Speak.Client" />
   After this change, <pipelines><speak.client.parseRenderingParameter> pipeline looks like this in a clean Sitecore installation:
   
   <speak.client.parseRenderingParameter>
    <processor type="Sitecore.Web.Pipelines.SetAttribute.ParseDataBinding, Sitecore.Speak.Client" />
    <processor type="Sitecore.Web.Pipelines.SetAttribute.ParseContextItemValue, Sitecore.Speak.Client" />
    <processor type="Sitecore.Web.Pipelines.SetAttribute.ParseFormValue, Sitecore.Speak.Client" />
    <processor type="Sitecore.Web.Pipelines.SetAttribute.ParseQueryStringValue, Sitecore.Speak.Client" />
    <processor type="Sitecore.Web.Pipelines.SetAttribute.ParseSessionValue, Sitecore.Speak.Client" />
    <processor type="Sitecore.Web.Pipelines.SetAttribute.ParseAppModelValue, Sitecore.Speak.Client" />
    <processor type="Sitecore.Web.Pipelines.SetAttribute.ParsePageModelValue, Sitecore.Speak.Client" />
   </speak.client.parseRenderingParameter>
9. In the <pipelines> section, add the following processor to <speak.client.resolveScript> pipeline after <processor type="Sitecore.Resources.Pipelines.ResolveScript.Rule, …" /> processor:
   
   <processor type="Sitecore.Resources.Pipelines.ResolveScript.Pipeline, Sitecore.Speak.Client" />
   After this change, <pipelines><speak.client.resolveScript> pipeline looks like this in a clean Sitecore installation:
   
   <speak.client.resolveScript>
    <processor type="Sitecore.Resources.Pipelines.ResolveScript.Main, Sitecore.Speak.Client" />
    <processor type="Sitecore.Resources.Pipelines.ResolveScript.Rule, Sitecore.Speak.Client" />
    <processor type="Sitecore.Resources.Pipelines.ResolveScript.Pipeline, Sitecore.Speak.Client" />
    <processor type="Sitecore.Resources.Pipelines.ResolveScript.ResolveBaseComponent, Sitecore.Speak.Client" />
    <processor type="Sitecore.Resources.Pipelines.ResolveScript.Controls, Sitecore.Speak.Client">
      <sources hint="raw:AddSource">
        <source folder="/sitecore/shell/client/Speak/Assets" deep="true" category="assets" pattern="*.js" />
        <source folder="/sitecore/shell/client/Speak/Layouts/Renderings" deep="true" category="controls" pattern="*.js,*.css" />
        <source folder="/sitecore/shell/client" deep="true" category="client" pattern="*.js,*.css" />
        <source folder="/sitecore/shell/client/speak/layouts/Renderings/Resources/Rules/ConditionsAndActions" deep="true" category="rules" pattern="*.js" />
        <source folder="/sitecore/shell/client/Business Component Library/Layouts/Renderings" deep="true" category="business" pattern="*.js,*.css" />
      </sources>
    </processor>
   </speak.client.resolveScript>
10. In the <pipelines> section, add the following pipeline at the end of the pipelines list:
    
    <mvc.buildPageDefinition>
     <processor type="Sitecore.Mvc.Pipelines.Response.BuildPageDefinition.ProcessMasterRendering, Sitecore.Speak.Client"/>
    </mvc.buildPageDefinition>
11. In the <sitecore> section, remove the <linkManager> element.
12. In the <sitecore> section, add empty <speak> section after <pipeline> section.

Changes to App_Config\Include\Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config

Tip: Most customers have only applied a small number of changes (if any) to the Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config file. In that case, we recommend that you simply download the clean config file using the link above and re-apply any changes that you've made to save time and to reduce the risk of making mistakes when the changes to the file.

The following changes have been made to the App_Config\Include\Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config file of Sitecore CMS 7.5 rev. 141003 (Initial Release) as compared to the App_Config\Include\Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config file of Sitecore CMS 7.2 rev. 140526 (Update-2).

1. In the <contentSearch> section, remove the <indexUpdateStrategies> element.
2. In the <contentSearch> section, remove the <databasePropertyStore> element.
3. In the <fieldNames> section, replace the following field element:
   
   <field fieldName="__smallcreateddate" storageType="YES" indexType="TOKENIZED" vectorType="NO" boost="1f" type="System.DateTime" settingType="Sitecore.ContentSearch.LuceneProvider.LuceneSearchFieldConfiguration, Sitecore.ContentSearch.LuceneProvider" />
   with this one:
   
   <field fieldName="__smallcreateddate"   storageType="YES"  indexType="TOKENIZED"   vectorType="NO" boost="1f" type="System.DateTime" format="yyyyMMdd" settingType="Sitecore.ContentSearch.LuceneProvider.LuceneSearchFieldConfiguration, Sitecore.ContentSearch.LuceneProvider">
    <analyzer type="Sitecore.ContentSearch.LuceneProvider.Analyzers.LowerCaseKeywordAnalyzer, Sitecore.ContentSearch.LuceneProvider" />
   </field>
4. In the <fieldNames> section, replace the following field element:
   
   <field fieldName="__smallupdateddate" storageType="YES" indexType="TOKENIZED" vectorType="NO" boost="1f" type="System.DateTime" settingType="Sitecore.ContentSearch.LuceneProvider.LuceneSearchFieldConfiguration, Sitecore.ContentSearch.LuceneProvider" />
   with this one:
   
   <field fieldName="__smallupdateddate"   storageType="YES"  indexType="TOKENIZED"   vectorType="NO" boost="1f" type="System.DateTime" format="yyyyMMdd" settingType="Sitecore.ContentSearch.LuceneProvider.LuceneSearchFieldConfiguration, Sitecore.ContentSearch.LuceneProvider">
    <analyzer type="Sitecore.ContentSearch.LuceneProvider.Analyzers.LowerCaseKeywordAnalyzer, Sitecore.ContentSearch.LuceneProvider" />
   </field>
5. In the <fieldNames> section, add the following field elements after the <field fieldName="__workflow_state" …> element:
   
   <field fieldName="_hash" storageType="YES" indexType="TOKENIZED" vectorType="NO" boost="1f" type="System.String" settingType="Sitecore.ContentSearch.LuceneProvider.LuceneSearchFieldConfiguration, Sitecore.ContentSearch.LuceneProvider">
    <Analyzer type="Sitecore.ContentSearch.LuceneProvider.Analyzers.LowerCaseKeywordAnalyzer, Sitecore.ContentSearch.LuceneProvider" />
   </field>
6. In the <defaultLuceneIndexConfiguration> section, remove the following element:
   
   <!-- CUSTOM FIELDS
       Custom fields allow you to store a field in different ways in an index. For example, if you have an analyzed field, you can
       create a custom field to store a version of the field that is not analyzed or store the original text value that has not
       been processed by the analyzer.
       Custom fields only support simple transformations. Use computed fields for more complex transformations, for example, if you
       want to store a date field in a different format.
   -->
   <fields hint="raw:AddCustomField">
    <!-- If you have some GUID-based fields in the index that you would like to merge into your Tag Repository, you can add
         these fields here.
         EXAMPLE: In a template, create a multilist field called "__yourtags". To add the tags selected in this field to the
         __semantics field, add the following custom field:
    -->
    <!--<field luceneName="__semantics"        storageType="no" indexType="tokenized" multivalued="true">__yourtags</field>-->
   </fields>
7. In the <fields hint="raw:AddComputedIndexField"> section, replace the following field element:
   
   <field fieldName="__smallcreateddate" >Sitecore.ContentSearch.ComputedFields.SmallCreatedDate,Sitecore.ContentSearch</field>
   with this one:
   
   <field fieldName="__smallcreateddate" >Sitecore.ContentSearch.ComputedFields.CreatedDate,Sitecore.ContentSearch</field>
8. In the <fields hint="raw:AddComputedIndexField"> section, replace the following field element:
   
   <field fieldName="__smallupdateddate" >Sitecore.ContentSearch.ComputedFields.SmallUpdatedDate,Sitecore.ContentSearch</field>
   with this one:
   
   <field fieldName="__smallupdateddate" >Sitecore.ContentSearch.ComputedFields.UpdatedDate,Sitecore.ContentSearch</field>
9. In the <indexFieldStorageValueFormatter> element, add the following converter elements at the end of converters list in <converters> section:
   
   <converter handlesType="Sitecore.ContentSearch.IIndexableId, Sitecore.ContentSearch" typeConverter="Sitecore.ContentSearch.Converters.IndexableIdConverter, Sitecore.ContentSearch" />
   <converter handlesType="Sitecore.ContentSearch.IIndexableUniqueId, Sitecore.ContentSearch" typeConverter="Sitecore.ContentSearch.Converters.IndexableUniqueIdConverter, Sitecore.ContentSearch" />
10. In the <settings> section, remove the following settings at the top of the settings list:
    
    <!-- CONTENT SEARCH - DEFAULT INDEX TYPE
         This setting specifies the index type that should be used when an item appears in more than one index.
    -->
    <setting name="ContentSearch.DefaultIndexType" value="Sitecore.ContentSearch.LuceneProvider.LuceneIndex, Sitecore.ContentSearch.LuceneProvider" />
    
    <!-- CONTENT SEARCH - DEFAULT INDEX CONFIGURATION PATH
        This setting specifies an XPath expression that points to the default index configuration. The default configuration is used for
        every index that does not have a specified configuration.
    -->
    <setting name="ContentSearch.DefaultIndexConfigurationPath" value="contentSearch/indexConfigurations/defaultLuceneIndexConfiguration" />

Changes to the following files:

• Sitecore.ContentSearch.Lucene.Index.Core.config
• Sitecore.ContentSearch.Lucene.Index.Master.config
• Sitecore.ContentSearch.Lucene.Index.Web.config
• Sitecore.ContentSearch.Lucene.Indexes.Sharded.Core.config.example
• Sitecore.ContentSearch.Lucene.Indexes.Sharded.Master.config.example
• Sitecore.ContentSearch.Lucene.Indexes.Sharded.Web.config.example
• Sitecore.ContentSearch.Solr.Indexes.config (this file does not exist and does not need to be upgraded if you are not using the Solr provider for Sitecore.ContentSearch)

Notice that the following changes must be made to all Sitecore.ContentSearch index definitions in the files mentioned above, as well as any custom index definitions that you might have in your solution.

1. For each index definition, replace the existing value of the ref attribute of the <param desc="propertyStore" …> node from “contentSearch/databasePropertyStore” to “contentSearch/indexConfigurations/databasePropertyStore”.
   
   After this change, <param desc="propertyStore" …> looks like this in a clean Sitecore installation:
   <param desc="propertyStore" ref="contentSearch/indexConfigurations/databasePropertyStore" param1="$(id)" />
2. For each index definition, update the ref attribute value of the <strategy> node in the <strategies hint="list:AddStrategy"> element in the following way: paths like this “contentSearch/XXX” need to be update to the paths like this “contentSearch/indexConfigurations/XXX”
3. Repeat the steps for each of the files mentioned above.

Changes to the following files:

• Sitecore.ContentSearch.Lucene.Index.Core.config
• Sitecore.ContentSearch.Lucene.Index.Master.config
• Sitecore.ContentSearch.Lucene.Index.Web.config

After the <locations> element, add the following elements. We recommend that you add the element to keep your file up-to-date, but this step does not affect the functionality of the system:

<!--
<shardingStrategy type="Sitecore.ContentSearch.LuceneProvider.Sharding.LucenePartitionShardingStrategy, Sitecore.ContentSearch.LuceneProvider">
 <param desc="shardDistribution">4</param>
</shardingStrategy>
-->

<!--
<shardFolders hint="raw:AddShardFolderPath">
 <shard shardName="shard1" shardRootFolderPath="c:\Data\Indexes" />
 <shard shardName="shard2" shardRootFolderPath="c:\Data\Indexes" />
 <shard shardName="shard3" shardRootFolderPath="c:\Data\Indexes" />
</shardFolders>
-->

Changes to App_Config\Include\Sitecore.ContentSearch.Solr.Indexes.config

Notice: This file does not exist and does not need to be upgraded if you are not using the Solr provider for Sitecore.ContentSearch.

Tip: Most customers have only applied a small number of changes to the Sitecore.ContentSearch.Solr.Indexes.config file. In that case, we recommend that you simply download the clean config file using the link above and re-apply any changes that you've made to save time and to reduce the risk of making mistakes when the changes to the file.

The following changes have been made to the App_Config\Include\Sitecore.ContentSearch.Solr.Indexes.config file of Sitecore CMS 7.5 rev. 141003 (Initial Release) as compared to the App_Config\Include\Sitecore.ContentSearch.Solr.Indexes.config file of Sitecore CMS 7.2 rev. 140526 (Update-2).

1. In the <contentSearch> section, remove the <indexUpdateStrategies> element.
2. In the <contentSearch> section, remove the <databasePropertyStore> element.
3. In the <typeMatches hint="raw:AddTypeMatch"> section, add the format attribute with the value “yyyy-MM-dd'T'HH:mm:ss.FFF'Z'” for the <typeMatch typeName="datetime" … > element.
   After this change, <typeMatch typeName="datetime" … > looks like this in a clean Sitecore installation:
   
   <typeMatch typeName="datetime" type="System.DateTime" fieldNameFormat="{0}_tdt" format="yyyy-MM-dd'T'HH:mm:ss.FFF'Z'" settingType="Sitecore.ContentSearch.SolrProvider.SolrSearchFieldConfiguration, Sitecore.ContentSearch.SolrProvider" />
4. In the <fieldNames> section, rename all fieldType elements in the list to field and add the following field elements to the list after <field fieldName="__created_by" …/> field element:
   
   <field fieldName="__smallcreateddate" returnType="datetime" format="yyyy-MM-dd'T'00:00:00'Z'" />
   <field fieldName="__smallupdateddate" returnType="datetime" format="yyyy-MM-dd'T'00:00:00'Z'" />
   
   After this change, <fieldNames> section looks like this in a clean Sitecore installation:
   
   <!-- This allows you to map a field name in Sitecore to the index and store it in the appropriate way -->
   <!-- Add schema fields here to enable multi-language processing -->
   <fieldNames hint="raw:AddFieldByFieldName">
    <field fieldName="__created_by"         returnType="string" />
    <field fieldName="__smallcreateddate"   returnType="datetime" format="yyyy-MM-dd'T'00:00:00'Z'" />
    <field fieldName="__smallupdateddate"   returnType="datetime" format="yyyy-MM-dd'T'00:00:00'Z'" />              
    <field fieldName="__workflow_state"     returnType="string" />
    <field fieldName="extension"            returnType="text" />
    <field fieldName="title"                returnType="text" />
   </fieldNames>
5. In the <exclude hint="list:ExcludeField"> section, remove the following element:
   
   <Hidden>{39C4902E-9960-4469-AEEF-E878E9C8218F}</Hidden>
6. In the <defaultSolrIndexConfiguration> section, remove the following element:
   
   <!-- COPY FIELDS
       Copy fields allow you to store a field in different ways in an index. For example, if you have an analyzed field, you can
       create a copy field to store a version of the field that is not analyzed or store the original text value that has not
       been processed by the analyzer.
       Copy fields only support simple transformations. Use computed fields for more complex transformations, for example, if you
       want to store a date field in a different format.
   -->
   <fields hint="raw:AddCopyField">
    <!-- If you have some GUID-based fields in the index that you would like to merge into your Tag Repository, you can add these
         fields here.
         EXAMPLE: In a template, create a multilist field called "__yourtags". To add the tags selected in this field to the
         __semantics field, add the following custom field:
    -->
    <!--<field fieldName="__semantics" returnType="stringCollection">__yourtags</field>-->
   </fields>
7. In the <fields hint="raw:AddComputedIndexField"> section, replace the following field element:
   
   <field fieldName="__smallcreateddate" returnType="string" >Sitecore.ContentSearch.ComputedFields.SmallCreatedDate,Sitecore.ContentSearch</field>
   with this one:
   
   <field fieldName="__smallcreateddate" returnType="string" >Sitecore.ContentSearch.ComputedFields.CreatedDate,Sitecore.ContentSearch</field>
8. In the <fields hint="raw:AddComputedIndexField"> section, replace the following field element:
   
   <field fieldName="__smallupdateddate" returnType="string" >Sitecore.ContentSearch.ComputedFields.SmallUpdatedDate,Sitecore.ContentSearch</field>
   with this one:
   
   <field fieldName="__smallupdateddate" returnType="string" >Sitecore.ContentSearch.ComputedFields.UpdatedDate,Sitecore.ContentSearch</field>
9. In the <indexFieldStorageValueFormatter> section, add the following converter elements at the end of converters list in <converters hint="raw:AddConverter"> section:
   
   <converter handlesType="Sitecore.ContentSearch.IIndexableId, Sitecore.ContentSearch" typeConverter="Sitecore.ContentSearch.Converters.IndexableIdConverter, Sitecore.ContentSearch" />
   <converter handlesType="Sitecore.ContentSearch.IIndexableUniqueId, Sitecore.ContentSearch" typeConverter="Sitecore.ContentSearch.Converters.IndexableUniqueIdConverter, Sitecore.ContentSearch" />
10. In the <settings> section, remove the setting with name “ContentSearch.DefaultIndexType”.
11. In the <settings> section, remove the setting with name “ContentSearch.DateFormat”.

Changes to App_Config\Include\Sitecore.ItemWebApi.config

Tip: Most customers have only applied a small number of changes (if any) to the Sitecore.ItemWebApi.config file. In that case, we recommend that you simply download the clean config file using the link above and re-apply any changes that you've made to save time and to reduce the risk of making mistakes when the changes to the file.

The following changes have been made to the App_Config\Include\Sitecore.ItemWebApi.config file of Sitecore CMS 7.5 rev. 141003 (Initial Release) as compared to the App_Config\Include\Sitecore.ItemWebApi.config file of Sitecore CMS 7.2 rev. 140526 (Update-2).In the <sitecore> section, add the following element at the end: